The University of Tennessee

EF 230 Spring, 2012

Computer Solution of Engineering Problems

Main Navigation:

• Announcements
• Instructor/GTAs
• Syllabus
• Calendar
• Section Info
• Procedures

Resources

• Labs
• Homeworks
• Projects
• Exams
• Drop Box
Help
• Help Sessions
• Discussion Board
• Search m-files
• Example m-files
User: wschlete
• Control Panel
• Student Lists
• Grade Entry
• Grade Stats
• Edit page
• Browse
• Logoff
Same page for ...
• EF 105
• EF 151
• EF 152
• EF 402

EF 230 Spring, 2012 Feedback

Current date:	Tue Jan 26, 2016 12:43:43
Start date:	Tue Apr 26, 2016 0:00:00
100% credit date:	Sun May 6, 2012 23:59:59
Current grade:

Too early - this form is not available yetToo late - this form has expired

Please take a few minutes and give us feedback on the class. Your constructive comments are invaluable to us in helping improve the class each semester. You will received extra credit for completing this form. Thanks.

Labs

Rate the overall quality of the EF 230 class.

28% (30/109) Very good (1) 61% (66/109) Good (2) 7% (8/109) Average (3) 4% (4/109) Marginal (4) 1% (1/109) Poor (5) 0% (0/109) N/A (0) Avg: 1.90, NZAvg: 1.90, sum=207, cnt=109, nzcnt=109

Comments/suggestions for improving EF 230:

2.  I think it might be beneficial to make it actually a longer class with more class time to learn the material. 4.  Homework assignments would be more constructive if they involved coding instead of just being multiple choice. 5.  see below 6.  none 7.  Well it would be nice if the class actually covered everything that was in the homework. 8.  spend more time on the logic of for and while loops(maybe one more lecture) 12.  Don't overwhelm, the students. 14.  Make it a three credit hour class because of the amount of work that is required to form programs for the projects and home works. 15.  The last few lectures seemed to just be time fillers. I think I would have rather had a few quick review lectures to prepare for the final exam 16.  Some of the material in the labs seemed kind of rushed, which led to said material not being covered very well/in-depth. Mix the homework up a little more, adding in more coding-like problems more often. 17.  a little bit slower in the course..and fewer materials to cover 18.  Maybe a few easier projects just after the semester begins would help. 21.  Perhaps reorganizing the material such that the level of difficulty increases. The second project seemed to be the most difficult for me. I would have benefited from doing simpler projects such as the Slideshow and Data analysis first. The slideshow / Data Analysis projects were where Sub-functions really sunk in. Had I understood more completely what the purpose of sub-functions were, I might have had an easier time with the Polygon project. 22.  This course provides a good understanding of MATLAB and this is really useful for solving Math or Engineering problems. 23.  Adding more review problems for tests 25.  The material too dense for the amount of time given and the problems given on the exam are also too difficult for the time given. While the questions would be fair during homework, on the spot coding is far trickier even for what can be for a seemingly simple problem. 26.  Very good, tough to learn a new language. Good idea to see it as such and be repitisous on key elements. 27.  More freedom on projects (like the final project) and less emphasis on exams. Coding is learned through necessity, and this necessity comes from later classes. 28.  More time/better preparation for the HW. I felt that the HW was incredibly difficult compared to what we were taught in class. If the HW is going to be such a high difficulty, make it worth less. 29.  Some of the labs were crammed with too much information. If possible it would be great if you could eliminate some information or not expand on an unimportant topic. 30.  better preparation for test really/ or lesson the amount required for the test 31.  None 32.  I would suggest more in-class assignments. i.e. As a class use fmincon to compute this value. 33.  I did not really like the complete multiple choice homeworks, but they changed to half multiple choice and work problems so it's not that big of a problem. 34.  when the GTAs talk during class, please try not to walk along the corridor (between the two sections of computers). Its quite frustrating when I can't see the board because GTAs are blocking the view all the time. Other than that, everything is good! :) 35.  I feel like for a two hour course there was way too much outside work required. I had to spend more time on this class than my three and four hour classes. 36.  I feel like it was a lot of work for only a 2 hr class. 37.  If you actually want us to learn MATLAB then make the course more than 2 hours and if you just want us to simply have been exposed to it than make sure the tests are made accordingly. 38.  For the homework that is assigned giving more problems that would be more like the exam questions would be, in my opinion, more helpful then the multiple choice questions that are given in the homework. 39.  It makes so much sense the second time around. 40.  Give more leadway into other programming languages. 42.  make it a three hour class 43.  I would like to somehow see more exciting or humorous things incorporated in lecture to maintain overall interest in the material. 44.  I feel like this class is more work than it's worth. I only get 2 hours of credit, but yet I do more work in here than a 4 hour class. 45.  Less homework more projects 46.  Better examples. 47.  more focus on stuff we will use less just trying to cover everything 48.  Hw solutions posted after assignment is due 51.  Possibly a little more clearer on why points were taken off on test and projects 52.  none 53.  Have more TA's at help sessions, overall the most well structured class I have ever had in college. Workload is perfectly assigned and reasonable. 54.  Less students, more one on one time. 55.  It would be a lot easier at a slower pace. 56.  More diverse examples in class, less steep penalties on hw 57.  More help sessions. With so many people it is hard to have one on one time with students but maybe only have specific Gta's for help sessions or have professor schleter lead a help session. 58.  Get rid of that second project that creates random points and makes a circle out of them. It required so much more time than the other projects. 59.  Letting us do problems in class. 61.  It was great all around frustrating but i enjoyed the class. It is a lot of work and time for just two hour credit though. 62.  Changing the homework to more coding problems and less multiple choice problems. 63.  The class was interesting and taught MATLAB well. I feel comfortable with MATLAB which is an achievement. 64.  Can't say much. 65.  This class should definitely be a 3 credit hour course. I have had more homework and projects in this class than in any of my other 3 hour courses which is very confusing. I spent about twice the amount of time outside of class working on projects and homeworks for this class than any of my other classes this semester. The tests were extremely difficult and covered a whole lot of information to only have 3 problems of hard code. 66.  None. 67.  Multiple choice on tests, not just short coding answers. 68.  Can't think of anything. The class was very good. 69.  Make the class a bit more interesting somehow. Maybe make the in class work cooler in some way 70.  Cooler projects 71.  The class is awesome! 72.  Some things in the lab seem trivial, feel like we spent a lot of time on some easy things and just rushed over some other useful things. 73.  I think y'all did a good job-- it could be a little less boring. However, I know that's hard to do. 74.  More help with exams, it seems like a lot of the stuff on the exams wasn't covered in the review. Also, if we are going to have practice problems, they are only helpful if we can see the solutions. A test case is great, but I had times that I may have been struggling to get the correct answer, and there was no solution so I couldn't find my errors. 75.  have a few more multiple choice questions on the tests 76.  Overall the class is very good and informative, no real suggestions, maybe have assigned projects based on certain engineering problems for students in different fields i.e. Electrical doing electrical problem, Mechanical doing mechanical problems 77.  The class is overall good, I would be more interested in learning more of the simulink type stuff, which will probably be used more by non computer engineering majors. 78.  Be more specific on what is expected of us on the exams. 79.  cant think of anything 80.  I thought that the course was very good overall. The exams are challenging, but there are many other opportunities to improve grades. (HW,projects,lab participation) 81.  It is better to put more time to focus on the projects, because that is how student can use thier knowledge. 82.  the T.A are very good... 83.  none 84.  Less difficult projects. Too many assignments for a 2-hour credit course. 85.  none 86.  none 87.  Not forcing me to take it. Two credit hours that could have been invested into something more valuable to build my engineering skill set. As a Chemical Engineer, I'm NOT going to use MATLAB in the future. 88.  A list of the functions we would need to know for the exams so we could review better or more details in the online labs again from helping with review. 89.  None, I thought my TA's did a great job and was much more satisfied with my teachers in this class as opposed to my 105 teacher. 90.  Some of the project/exam grades could have been returned more quickly. Not a big deal though. 91.  Good class, wish we could cover some AutoCad. 92.  The lab pages seem a little minimal and are hard to learn from when reviewing the material after class... I think a lot of study time could be saved if they had more information about what functions we used, or some tips about trickier processes. 94.  Cover fewer topics 95.  none 96.  None 97.  homeworks could have more problems to work rather than multiple choice 101.  Exam reviews.... 102.  More notes. 106.  None. 108.  The sections on images/sound and how to make movies could be explained further.

GTAs

Rate the overall quality of the Ryan Graham's in presenting and explaining the material. Use N/A if he never presented the lab in your section.

31% (34/109) Very good (1) 30% (33/109) Good (2) 1% (1/109) Average (3) 0% (0/109) Marginal (4) 0% (0/109) Poor (5) 38% (41/109) N/A (0) Avg: 0.94, NZAvg: 1.51, sum=103, cnt=109, nzcnt=68

Rate the overall quality of the Stephen Phillips's in presenting and explaining the material. Use N/A if he never presented the lab in your section.

53% (58/109) Very good (1) 31% (34/109) Good (2) 1% (1/109) Average (3) 0% (0/109) Marginal (4) 0% (0/109) Poor (5) 15% (16/109) N/A (0) Avg: 1.18, NZAvg: 1.39, sum=129, cnt=109, nzcnt=93

Rate the overall quality of the Everett Stiles's in presenting and explaining the material. Use N/A if he never presented the lab in your section.

47% (51/109) Very good (1) 33% (36/109) Good (2) 6% (6/109) Average (3) 1% (1/109) Marginal (4) 2% (2/109) Poor (5) 12% (13/109) N/A (0) Avg: 1.42, NZAvg: 1.61, sum=155, cnt=109, nzcnt=96

General comments/suggestions on GTAs:

1.  I did not have him as a TA. 2.  Both Ryan and Stephen were excellent at presenting the material in my class. 4.  They both did a great job explaining the material, but at times they did move a little fast. 5.  TA's were good 6.  none 7.  When going through example problems if they went a little bit slower, so it could be copied down. 8.  Everett would be much better if he didn't seem pompous when he was talking to you or the other GTAs. 11.  All friendly and helpful. Stephen's hair is pretty great, too. 12.  Very fast 13.  Stephen seemed to be the most approachable; both he and Ryan gave very good answers when I came to them with questions. I didn't work with Everett as much, but he came off somewhat condescending even though he was very helpful and knowledgable. 14.  N/A 15.  The TA's were very helpful. They were able to answer any questions that arose during class time as well as the help sessions 16.  The GTAs were great. Very helpful and presented the material very well. 17.  GTAs could show the screen for the students a little longer before he moves on to a new page 18.  The GTAs did an excellent job explaining the concepts and details of coding in MATLAB. 20.  All of the TAs were awesome. They were all very helpful and nice! 21.  Overall I was very happy with their help. I think it would benefit help sessions if more than one were available. Too many people at help sessions made it difficult for one TA to make an impact. 22.  They really know their stuff and are very helpful, always willing to assist students in understanding errors encountered or coding in general. Help sessions provide a good resource for students as GTAs could address their needs individually. 23.  All the GTA's taught the material well 24.  I believe Stephen and Everett worked well together. They were a good balance. 26.  Very good overall know what they are talking about, Sometimes they move pretty quickly as the course material is repitition for them. 27.  Stephen is the man! 28.  They did a good job. 29.  Both Everett and Stephen were great TA's. They were very understanding if something was not clicking and also gave their best effort to make sure that the material was being absorbed 30.  Ryan and Everett were solid TA's who really know their stuff especially Everett though sometimes he comes off as knowing too much 31.  Very informative teaching the material 32.  No suggestions. Learned alot from you guys 33.  Nothing really, I did not mind the TA's or the way the course was taught. 34.  They're all very helpful and willing to help. It was a little frustrating at the beginning of the semester when students literally know nothing about MATLAB or programming. please understand that we're not as smart as you all are.... Towards the middle/ end of the semester everything gets better :) 35.  N/A 36.  Sometimes when asking for help I didn't exactly leave with the answer that I needed to move forward with what I was doing. 37.  Putting up things you went through in class would be helpful because I know you all have to get through it but you guys do type very fast. Also if the examples posted could have more comments in them that would also be nice. 38.  They were all very good and very helpful when someone had a question that needed to be answered. They were very knowledgeable about the topics covered in class. 40.  Not really, I think they are great TA's. They always answered all of my questions throughly. 42.  My TA's were stephen and everett and I thought they both did a very good job at explaining everything I needed to know this semester. 43.  I wish Everett would be more helpful in guiding me to write code.. 44.  Everett and Stephen were a lot of fun and very helpful. 46.  None 47.  needed to actually explain more 48.  Good overall, sometimes a little quick and short tempered 49.  Very friendly and approachable. 51.  I think they should all grade the same. On my project 3 stephen graded it and took off 10 points for something and everett looked at it and said he would not have taken any off 52.  Good teamwork 53.  Was not in Ryans' class but he gave good advice during help sessions, Stephen was very easy to talk to and get along with and also gave good advice and made breaking down difficult problems a bit more manageable, Everett is incredibly gifted in computer skills and has plenty of useful knowledge to pass on. 54.  We need more one on one time. 55.  TAs are great 56.  I have none. 57.  Both were really good. 58.  They were pretty clear explaining everything this semester. Sometimes, though, they would cover up their code with a figure window. It was slightly annoying but i still got the code in the end. 59.  They were excellent. 60.  . 61.  They always were right there for me. They are nice and fun and very helpful. 62.  The GTAs that taught my class were very good. They were very well informed about the information and were good at keeping the class entertained with the material. 63.  TAs were very helpful and went out of their way to make sure we understood the material. 64.  Stephen is very helpful. He knows most of the material and how to explain it to others. Stephen is just smart. He knows all the answers to your questions, but the flaw there is he sometimes explains it in a way you can't understand (too technical or terminology). 65.  Both GTAs were very helpful and informative. Stephen did a great job of helping me better understand things that I didn't get at first. 66.  None. 67.  It's obvious that Everett knows more about Matlab and coding but he isn't as good of a teacher as . Stephen is a much more well better spoken. 68.  Very helpful 69.  I hate when they answer my question with a question, which happens quite often. I know they are trying to get me to learn it but its extremely unhelpful and makes the individual student look stupid for even asking a question 70.  Helpful overall 71.  None 72.  Very helpful when needed, willing to take extra time to help with projects and things. 73.  Did well-answered questions with knowledge. Sometimes it was a bit too specific though. 74.  I loved working with Ryan as he was very helpful and a great teacher. Everett was very knowledgeable, but he was not very effective as a teacher or tutor. 75.  they both know what they are talking about. but Everett could try to help out a little more in help sessions instead of trying to make us figure it out on our own. 76.  TAs were very good and very helpful in class time. They were very informative and had a great understanding of Matlab and programming in general, a very positive overall experience. 77.  The TAs were knowledgeable about the material, they were able to help when I had a question, I have no complaints. 78.  My GTAs were both very knowledgeable and helpful to my EF 230 needs. 79.  they ask too many basic questions and expect us to answer when they have nothing to do with the class. example "2+2=? class, come on guys". i understand that they are trying to make sure the class is paying attention but sometimes it gets to be too much. the people who are going to pay attention will attention. that was a bad example but the only one i could think of. but i do think they are both very knowledgeable and good at knowing what is being asked by a student and how to help. 80.  I thought that the GTAs did a great job of covering the material, going over examples, and answering questions. 81.  GTAs need some skill to attract student's attention sometimes. 82.  n/a 83.  none 84.  N/A 85.  awesome. keep doing what youre doing. 86.  none 88.  overall attitude towards the students. 89.  None 90.  Where are the female GTAs???? :) 91.  Good job overall. Having two was helpful in that if one had trouble explaining something there was always an alternative way to explain it 92.  Only problem was when the computer couldn't run certain processes fast enough to keep up with the teaching. Even if the TA's had slowed down we probably wouldn't finish class in time, but that problem didn't happen often. 93.  Stephen was very helpful. He explained matlab in terms that i could understand 94.  Did a good job 95.  none 96.  Some of the harder concepts to understand were not spent enough time on but overall they were very helpful in learning the material. 97.  were able to help sufficiently when questions were asked 98.  No real suggestions. They both knew what they were talking about and were clear/concise about what they were teaching. They both answered questions and were very helpful when asked. 99.  they do a good job, keep it up 105.  little vague about certain topics that turned up on tests 106.  None. 108.  They presented the material well.

Resources

Rate the overall quality of the EF 230 web site.

60% (65/109) Very good (1) 38% (41/109) Good (2) 2% (2/109) Average (3) 1% (1/109) Marginal (4) 0% (0/109) Poor (5) 0% (0/109) N/A (0) Avg: 1.44, NZAvg: 1.44, sum=157, cnt=109, nzcnt=109

General comments/suggestions on web site:

2.  n/a 4.  For the multiple-choice homework, it would be better if you could copy/paste from the choices. 5.  website is good 6.  none 11.  Keep on keepin' on 12.  Nice Layout 13.  not very exciting, but easy to use 14.  N/A 15.  I like the EF website. I think it is much more effective than the use of blackboard 16.  Great website layout. It is very easy to navigate and find things you need. 17.  the web site is good! 18.  My only suggestion would be to allow a log in to last longer before its prompts the user to log back in. 19.  A bunch of the labs didn't have much information on the website. It would be nice to go back and see at least bullet points (or more specific bullet points) and definitions of what we talked about in each section of the lab as reference. 20.  The only issue that I had with the website was that I wish labs were fully uploaded sooner. I usually like to look over the content before class, but I wasn't able to do that. 22.  Information are arranged systematically on the website. All the features such as project section, homework section, grades etc. makes accessing information easy. The discussion board is a cool feature for students to have discussions and have questions answered by students themselves or the professor. 23.  The website was very helpful and provided a lot of useful tools 26.  Is user friendly could find anything I needed answered for course on site. 28.  Website is one of best I've seen for classes 29.  Easy to navigate and find what you are looking for. 30.  none 31.  Labs could use more example codes. 32.  None. 33.  I'm not a very strong programmer so I appreciate that projects are a large portion of our grade as well so I can beef up my weak test scores. 34.  very user friendly. 35.  N/A 36.  N/A 37.  None the website is layout out very well. 38.  Perfect!! 39.  There should be more examples on the website than the ones we go over in class. And it would be helpful if our GTAs posted the code we wrote in class so if we weren't able to copy it all, we would still have it. 40.  Very well put together. I like how there is the grade sheet and estimator. It really helps you with time managment. 42.  For some reason I could not see some of the material on the website when I would use firefox on my computer at home. 43.  When I click on a link in the lab section and press the back button to go back to the lab, the window un-expands the lab section. It would have saved me a headache when studying for my tests if I did not have to re-expand the sub-tabs every time I clicked the back button. 44.  The website looks great and is easy to navigate. 45.  having it seperate from blackboard was annoying 46.  None 47.  really easy to use 48.  no complaints, best departmental website 49.  Maintains itself very well, certainly better than OIT. 51.  great 52.  none 53.  Easy to navigate and very user friendly no changes necessary in my opinion. 54.  Site is well put together. 55.  None 56.  Less penalty for wrong answers 58.  Dont make the questions a one click answer. I have missed a few because i scroll with the track pad and accidentally click one while scrolling. 59.  Nothing 60.  . 62.  I have been using the engineering wbesites for classes for two years and never had a problem with any of them. No reason to change anything. 63.  The website is fine. 64.  I've always loved the way the EF websites are setup. They keep me up to date and I know exactly when I need to do stuff. I wish every class was run like the EF website. 65.  The website is great. 66.  I like the immediate feedback on being right/wrong on the homework. It irritates me when I'm viewing a lab page and then click on an example MATLAB file within that lab and the hit the back button to go back to the lab... the lab is collapsed again and I have to search for the section I was previously looking at. It would be nice if when you click on examples and then clicked back to the lab you would view page the way it was before you clicked out of it. 67.  I have gotten used to using the website over the past two years and it is very easy to use and I dont think it would be wise to change it 68.  The website is clear and well laid out, but sometimes it's still hard to look for notes on a specific topic unless you remember what general topic the notes are under. The search function for m-files is very useful. I think it would be helpful if the search function is extended to include notes as well. 69.  none 70.  None 71.  None 73.  Loved it. Easy to navigate and use. 74.  Make sure the grade estimator actually works for the entire semester, at the beginning of the semester there was no 3rd exam place on the estimator, and messed up the estimation. 75.  good 76.  EF 230 website is very easy to access and use, pretty much everything you need to do well in this class is there. 77.  The website is laid out well, stuff is easy to find and I don't have any suggestions for improvement. 78.  The website was great and easy to navigate. 79.  i cant think of anything to change on the website 80.  The website is designed well and is extremely helpful. 81.  good 82.  n/a 83.  none 84.  N/A 85.  none 86.  none 87.  The website works well. 88.  It was easy to use, don't feel like it needs to be changed any. 89.  The website is easy to use and I wouldn't change anything about it. 90.  Maybe there could be a MATLAB help file type of thing... except done by students and TAs with simple examples of every function and etc... might be impractical though 91.  none 92.  Again, just try to aim the site more to the students--it's easy to follow quickly once it's understood, but while learning the site can be a little lacking. 94.  Good website 95.  none 96.  Very easy to navigate and very helpful with labs and homework etc. 97.  easy to find needed materials 98.  This with the other EF websites are the best I've ever used for school work. 99.  i think the web site is well put together and makes homework easier to keep track of and everything else in the class when you put it that way 102.  The search was a little annoying. 106.  None. 108.  The clickable answers for the homework problems is a definite improvement. Don't like how it goes back to the top of the page after each question, though. 109.  For the first homework, post instructions that include pointing out that clicking on the answer enters that answer without confirmation.

What are your feelings on a textbook for this class?

11% (12/109) I would purchase a textbook if required (0) 16% (17/109) I would purchase a textbook if recommended (1) 73% (80/109) I don't think a textbook is needed (2) Avg: 1.62, NZAvg: 1.82, sum=177, cnt=109, nzcnt=97

Are there any other resources that you think might be useful as a formal part of this class?

2.  none 4.  Google is way faster than any textbook. 5.  none 6.  none 7.  n/a 11.  Nope 12.  More in-class examples 13.  In a computer science class i took before, there was a printed reference containing explanations of all the if blocks, logical operaters, for/while loops and several common functions that was very helpful to refer back to 14.  For each lab add a bullet point in that lab that has a list of all new function that were used for that lab. 15.  N/A 16.  Possibly having tutorial videos on some of the harder aspects of the class as extra reinforcement for the material. 17.  fun videos to relieve stress.. 18.  Not that I can think of 20.  n/a 21.  A Matlab users guide would be great. Perhaps even "Matlat for Dummies". 22.  N/A 23.  No, the website covers all the important topics 25.  Separate the lab and the lecture. While the help sessions are good, they need to be a scheduled part of the class as following the material while also practicing is difficult for those of us who cannot understand the material fast enough. 26.  Maybe Matlab for Dummies. I could have probaby used this book. 28.  A textbook is a great idea 29.  No. 30.  no 31.  No. The provided resources are good 32.  No 33.  Nope 34.  no. 35.  none 36.  N/A 37.  Maybe handouts. 38.  The Mathworks website?? 39.  Nope, I like having everything on the website. Easy access from anywhere. 40.  No, everything that you need is on the website or the matheworks help files. 42.  Not that I know of 43.  Not really. 44.  Just the general matlab help site, but you already reference those anyways. 45.  no 46.  None 47.  not really 48.  n/a 49.  n/a 51.  i do not think any others are needed 52.  none 53.  Perhaps at the very beginning of the semester be very persistent about explaining the necessary components of writing functions and how to properly define all of your variables in most efficient manner. 54.  Not that I know of. 55.  None 56.  A general problem tutorial available online 58.  no 59.  Other websites that would help us out. 60.  . 62.  Not really, the class is best when learned by example and trying to figure things out on your own. If I would have had a text book i would have been tempted to look at a bunch of examples and think I understand the problem, instead of actually working them out on my own and knowing I know the material. 64.  A brain is all you really need. 65.  Not really 66.  None. 67.  As long as you pay attention in class then it is an easy class. 70.  Not that I know of.. 71.  None the website covers most everything you need. 72.  Between the website and the matlab help site, I don't know how there could be any more resources needed. 73.  No. 74.  n/a 76.  None 77.  None. 78.  No. 79.  i cant think of anything 80.  no 81.  maybe GTAs can print some summary and give to the student before the exam. 82.  should get a textbook. 83.  none 84.  Not really 85.  none 86.  none 87.  I think the current format is fine. 88.  List of the more difficult major functions needed to be learned during the course. 89.  Nope. 90.  I do think a textbook could be very helpful. The built in help file in MATLAB is often tedious and confusing. Sometimes the website just doesn't have the information I'm looking for (or there is an obscure example somewhere). An effective textbook might help simplify the class for those who struggle with programming. 92.  I used other school's sites on matlab often, but never the same one multiple times--that said, I think our site should be 90% adequate at presenting the information, in case something could be missed in class or any other simple minor problems. 94.  None 95.  no 96.  I think a textbook would help learn concepts better. 97.  none 98.  I think a bigger focus on coding flow charts would be useful. Maybe simpler programs, but with flow charts, for projects. Or a project that is JUST a conceptual flow chart. 99.  I dont honestly think a textbook should be required. I think it might be helpful to lay out all the commands for someone who might not understand it so well so it might be good to have one on the syllabus if the student needs extra help. 100.  Some form of free comprehensive guide to programming would be nice. Either hard copies or in digital form 106.  Not really, we have access to anything we need to know about Matlab. 108.  The help tool offered in MATLAB and the material on their website seem to be sufficient. 109.  None come to mind. I'm not really all that familiar with programming stuff outside of this class.

Suggestions

From your viewpoint, what was good about this class?

1.  This course explained the use of MatLab very well. Before this class I did not know nearly as much about MatLab as I do now. 2.  I learned a lot about matlab and how to use if for other classes not just for simple matlab programs. 3.  clear requirements, interesting projects (most of the time), well divided lectures 4.  Learning Matlab 5.  the labs were good 6.  none 7.  learning about how to write a matlab code 8.  The homework and the instruction for the most part 9.  not much 10.  Since I will be taking MATH 231 next semester, the ode45 function seems like something I will use often to check my homework. I'm glad that this function was explained thoroughly. 11.  In class examples, multiple choice homework. 12.  the material covered was interesting 13.  I really liked always having the reference material organized in one place and being able to look back through the labs and examples on the website 14.  That I can now go into the work place and understand how to program a file with little to no problems 15.  I thought the class was well formatted 16.  The class progressed very well, having material build off of the past things nicely. 17.  THE GTAS 18.  The class ran smoothly and taught me a lot, including how to think like a coder. 19.  The homework problems helped understand the material greatly. Some were challenging and some were just a nice refresher. 20.  I really appreciated that there was always many ways to get help, be it during help sessions, on the discussion board, just asking in person, etc. I think this strong system of support definitely added a new level to the class - especially for those people who aren't the best at coding. I also appreciated that there were usually review questions before exams. 21.  It introduced me to the world of computer language and programming. A great start for any engineer. 22.  Lectures were conveyed clearly and examples demonstrated were very helpful in understanding the function and how to use a command. Online homeworks made things efficient as no paper work were needed. Projects were a really good way to practice and experiment on coding. I skipped EF classes before EF230 as a transfer student, and though I have dealt with MATLAB before in Math classes, I never learnt as much as I gained in this class.I find this class really helped me a lot on understanding how to do coding. 23.  All of the one on one time that was available for students 24.  I liked the projects. The projects helped me to actually learn and better understand Matlab instead of just knowing function names. 25.  Introduces programming. 26.  It forced you to solve many problems on your own, definately felt that i learned alot. 27.  Material presented at the very end. 28.  Learning how to manipulate MatLab 29.  The help session were awesome. They are a must have. 30.  being able to learn something new in more depth 31.  If you come to class, the TAs help you learn the material. 32.  I didn't really know how to do anything in Matlab from EF 105. Now I think that I can actually use Matlab to help on a work assignment. 33.  The projects and the homework, programming is almost like learning a foreign language sometimes. I appreciate the grade buffer so I don't have to spaz out about the tests. 34.  EF department in general is very helpful to students. MATLAB is very useful...not just this particularly program, but learning the skill of basic programming is important and useful to students in the future. 35.  I have a better understanding of matlab now. 36.  I did learn a lot from this class. Coming into it, I practically didn't know anything and I actually can write code for some simple problems now. 37.  We learned to how look up stuff from the help file since that was the most common statement said. I guess I also understand MATLAB better than before. 38.  It was a very well structured class, and had plenty of opportunities to receive extra help when it was needed. 39.  I like that I am able to use Matlab outside of this class. I feel like it's made up independent and we can fix our own errors when we run into them. 40.  Really introduced the idea of programming to our class. The user-friendliness of matlab is perfect for an undergraduate course. 41.  It was structured nicely and the website makes things a lot easier to learn and the material is more organized. 42.  I learned a lot about programming in general. Before this class I basically knew nothing and now I feel like I could at least figure out how to do most things using programming. 43.  I feel that it was effective in teaching me how to understand and write code, something I have always been interested in learning how to do. 44.  The TA's. 45.  projects 46.  The first module. 47.  the availability of the website 48.  Got a really good understanding of Matlab and confidence that I can learn other programs 49.  I enjoyed being taught by the TA's. I felt like they commiserated well with us. 50.  Learning about MATLAB and programming in general 51.  the organization and how well the GTAs knew their stuff 52.  Teaches you to find information on how to problem solve on your own. 53.  This class taught me valuable critical thinking skills and I also feel as though my computer coding and typing skills have improved a significant amount. 54.  I Liked the way you can look up all the labs we have done. 55.  The willingness of the TAs to help and answer questions 56.  I learned about general coding, not just matlab 57.  It covered the basics of so many things and it was cool to see that we learned how to code in so many different actual itnerfaces and that we werent just learning matlab. 58.  learning the language seemed like it will be pretty valuable. Looking at other languages, it seems like it will be easier to learn another language based on what i learned in matlab. 59.  The challenging projects , all the knowledge that I gained from this class 60.  The in-class examples and functions with comments helped when reviewing or when stumped by homework problems. 61.  The class just how it was taught. 62.  The GTAs definitely made the class. The were great at teaching the material. 63.  The class was good because it was a broad overview. 64.  I learned a lot. I picked up on new commands very easily for the most part. 65.  The amount of useful information I learned and will be able to apply in future classes. 66.  The last day... and the fact that this class will eventually come to an end. 67.  It was helpful learning for loops and if loops. 68.  The class teaches programming in Matlab, but the concepts presented in the class can easily be carried into other programming languages. 69.  It was a good introduction to math based computer systems 70.  Structure, website, format.. had a C++ ECE206(?) class that was set up terrible with a 2 lecture sections and 1 lab where you programmed. Wasn't effective. 71.  It teaches you the fundamentals of matlab while allowing you to experiment 72.  Things are very well explained, makes it easy to not get overwhelmed by what we are doing. Resources are abundant enough to make even seemingly difficult labs or projects doable. 73.  I learned a lot. Also, it is obvious how this could help me in the future as an engineer. 74.  I enjoyed the challenges associated with MATLAB and learning the basics of programming. 75.  the extra credit given and points given for attendance 76.  TAs were very good, class load is also very manageable, should prove to be a very useful tool moving forward in my engineering classes. 77.  The class was extremely useful in helping with other classes. The format was also good, somewhat laid back, which made it easy to learn the material in a way that didn't feel rushed. 78.  It has shown me how to display information and make certain calculations that will be very relevant to my later engineering classes. 79.  the flow from topic to topic and the TA s worked off of each other very well 80.  This class gave me a better understanding on how to use matlab to solve a variety of problems. 81.  student learn what the matlab can do. 82.  the T.A were very good 83.  Everything 84.  The in class examples and applications to other classes were very helpful. 85.  learned a lot about matlab that i can possibly use in other classes 86.  learning 87.  The fact that it's 2 credit hours thus will be affecting my GPA less. That I only had to endure it 2 times a week instead of 3. That it's the last time I will ever have to step foot in Estabrook, which alone should probably lower my health insurance. 88.  the format of the class was okay. 89.  The teachers did a good job explaining the material and moved at the right pace. I was able to follow everything they did. 90.  This was one of my favorite classes of the past two semesters. The TAs are knowledgeable and interested in what they're doing. The material is presented in such a fashion that one rarely seems overloaded. Good job. 91.  It taught me a lot about matlab, which in turn helped me with my classes. If I ever have a problem that is too much work to do by hand, I feel 100% confident in my ability to find a matlab solution. 92.  Learned how to do many useful things with matlab. I think all engineering disciplines should take the class, because y'all do an excellent job of showing what a useful problem solving tool matlab can be. 93.  it was challenging and made me think critically; therefore, it required alot of input on my part but it was very rewarding when you finally get something right. 94.  It teaches some valuable concepts 95.  introduced to computer programing and learning things to help me with other classes in the future 96.  Showed how programs such as matlab can solve real life problems must faster and more efficient if used the right way. 97.  the material covered during class were covered well 98.  The problem solving skills from this class go a long way even outside of class or programming in general. 99.  I like the way the grades are set up and that the homework is online, it helps me keep track of when its all due 100.  Very well explained. Decent pace. 101.  The Homeworks 102.  The information was great and very helpful and I do enjoy the fact that I can operate Matlab. 103.  The website containing all of the relevant information was incredibly useful. Even if I didn't make it to class (which wasn't *too* often) I could still catch up reasonably well and get back on track. 104.  I felt like the class was well laid out and presented and the material was thoroughly covered. 105.  It is hands on instead of just memorizing things. 106.  The projects were good, because they provide time to practice what you know while making sure you actually understand it. 107.  Information clearly presented, well organized. 108.  Learning about creating functions. 109.  It was good to learn the basic train of thought that goes into programming.

From your viewpoint, what was wrong with this class??

1.  Some of the topics felt a little boring sometimes, but other than that I do not have any complaints. 2.  The lack of writing code in the homework. 3.  ODEs were hard has I have never worked one on paper and so understanding what matlab was doing with it or how to program it was challenging and not very clear. 4.  There was a bit too much work for just a 2 unit class. The class should be 3 units. 5.  Projects were too hard. They did not reinforce what we had learned. 6.  none 7.  Well first, the project's were too hard because there were functions/commands that were to be inputed into the code that we had never learned. Also the amount of time that is spent on homework, and projects, this class needs to be a 3 hour credited class. From this class, I felt more of 'this is what matlab can do' instead of learning actually how it works and is done 8.  The tests seemed to go further into the topic than what we were doing in class/on homework 9.  having attendance as a grade. spending more time on this 2hr class than other 3hr classes 10.  The section of the class dealing with for and while loops seemed a bit rushed, and I didn't retain as much as I should have the first time I saw that. 11.  Too much material too fast. I think we would learn better with more in-class programming. Maybe for a grade? 12.  The speed was terribly fast 13.  It seems that more effort is expected of the student than most are willing to put in. 14.  N/A 15.  There were some lectures that i felt moved a little fast 16.  The varying degree of difficulty in the projects seemed a little off. The first project was far too easy, but the second project (at the time) seemed far too hard, with the last two being between the two extremes. It seemed like the polygon project should have been more towards the end of the semester. 17.  the lights!!! to much brightness...specially ones around the screen 18.  I wouldn't say anything was "wrong" with the class 19.  Some very useful tips for using MATLAB efficiently weren't disclosed until one of the last labs. 20.  Personally, I didn't really like the open-ended projects as much as the projects where I knew what I was supposed to do... I felt like with the open-ended projects I felt like I ended up doing a a lower-quality job because I didn't know where to go with a lot of things. ): 21.  Not enough real world examples of how Matlab is used by engineers at a job site. I can see it's trivial applications in academia and within computer engineering, but I have talked with plenty of engineers who have never used programming once in their careers. 22.  While project work time may give time for completion of project, if too long a time is given, students usually do not utilize the time well and becomes kind of a waste of time. Probably covering more material would be too heavy for students but I guess that time could be used to show more examples involving different situations. 23.  Some projects were a little too difficult and participation should be higher percent of grade 24.  Can't think of anything wrong with it. 25.  It is far too rigorous for what is a essentially a general education course for engineers. 26.  It was very fast, it would be better if this was a 3 credit course and more time could be spent on it. 27.  Too much emphasis on exams 28.  Tested/given hw of a higher level than we were taught 29.  I feel the projects should have more freedom, like the final project. 30.  i guess going a little fast at times 31.  None I can think of. 32.  . 33.  The homework was initially all multiple choice, but it was changed to have some workable problems so no complaint anymore about that. 34.  The help sessions are great. Very helpful. But sometimes (the few days before an exam or the day before a hard assignment is due) there are just too many students and not enough GTAs, that GTAs don't get a chance to help everyone in the session out. 35.  There were too many projects and all of the projects were due in the same week as our tests so it was hard to do both. 36.  The only thing I think is wrong is when I needed help, I didn't feel like I got the help I needed so I was still as lost as before resulting in never knowing the answer. 37.  IT'S A TWO HOUR COURSE! If you really want us to really understand and not just look up then make to course a longer one like Georgia Tech does or don't expect much. For example the coding exams the first one was alright, the second one wasn't anything like the posted practice problems and was useless as a study tool, and the third exam the image problem was a problem for a project not a test. 38.  The difficulties of the projects varied a lot, and the multiple choice parts of the homework were never really that useful. 39.  Sometimes we moved fast towards the beginning. I think we should have spent more time on functions since it is the basic of everything we do. 40.  At times, the pace of the class was going way to fast. Didn't seem there was time for learning in class. 41.  I can't think of anything. 42.  It was way too much work for a 2 hour class. 43.  I think Prof. Schleter should have come around more. 44.  The amount of work. 45.  test format 46.  Too many projects for a two hour course. 47.  covered way too much in not enough detail to actually get to understand and use everything 48.  Last few weeks of class seemed kinda pointless, could have used that time to better go over earlier material 49.  It isn't really something that can be avoided, but parts of the course are extremely dry. 50.  The difficulty of certain projects 51.  nothing 52.  nothing noticeably wrong with it 53.  There was a wide variety of information and it was difficult to get a solid grasp on certain concepts before we moved on to another topic; felt like I was playing catch up through much of the semester. 54.  after the lab is done, their should be commented examples of the in class problems 55.  A little too fast 56.  Very little room for error in some portions of the class 57.  Just not enough time one on one with students. It was hard to ask questions in class because it seemed almost overwhelmingly a lot and it was hard to have just one specific question without slowing the class down. 58.  i would have preferred java or c++. other than that, i guess the tests were sort of hard. 59.  The pace of the class 60.  . 61.  A little fast. but I just had to keep up 62.  The multiple choice homework problems were sometimes misleading. It just felt like some of them were trick questions. 63.  It went too fast at times and it seemed like a few things were brushed over. 64.  A few things were a bit tricky. I feel like they should have spent more time on certain topics. Some of these topics are: curve fitting, numeric differentiation, and integration. 65.  The tests were way too hard, should be more like the homeworks and all the projects and tests took a really long time to get back. We would have already started another project before we even got the grade for the one before back. 66.  MATLAB is the worst thing ever... and should not be a required class. I will NEVER use this program EVER again. 67.  there was a bit too much work for only a two hour class 68.  Can't think of any. I really enjoyed the class. 69.  It has very dry subject material 70.  Not enough time for the amount of stuff on the exam in my opinion. 71.  Nothing 72.  I felt that sometimes I could have been learning more. This is probably just because I have taken a programming class before, though. 73.  Unless you're interested in coding, it's very difficult to get yourself to pay full attention in class for the entire period. 74.  The class requires way too much time to only be worth 2 credit hours. We shouldn't have 2 classes of 75 minutes for only 2 credit hours. Also, the homework and project requirements made this class take way more time than it should have. 75.  the multiple choice homework and not getting to what some of the questions covered in class 76.  Exams were a little hard to complete in the allotted time, maybe I'm just slow but I did have difficulty finishing the exams. 77.  A few of the test problems were harder then the homework that was over the same material, which was evident by the number of people who didn't do quite as well. 78.  The speed was a little too fast for the way I like to learn. 79.  it was kind of hard for me to type out what one TA is typing into matlab and to pay attention to what the other TA is saying about what is being typed out. I dont know how this can be improved it might just be something i need to work on 80.  I felt like the exam problems were more difficult than necessary. It would have been more fair if the example problems had been more similar to the exam problems. 81.  there are no enough opprtunity for student to make innoations,and student struggle on how to make the code works. 82.  to much material. 83.  nothing 84.  The level of involvement for the course was not what it should be for a 2 hour course. 85.  it isn't really related to my major of chemical engineering 86.  being taught things and ta's saying "you won't use this, but..." 87.  The fact that it's 2 credit hour class that WILL be affecting my GPA. That I had to endure it 2 times a week instead of 0. Ok, I'll quit being snide now. I can understand the logic behind having a class like this. Computers serve an extremely important role in our lives today, both recreationally and professionally. But I do not see the value in this class. Let me make a list. 1. This class is far too much work for 2 credit hours. The effort required to succeed in this class even exceeded some 4 credit hour classes I have. How can you justify 17 homeworks, 4 exams, and 5 projects for a class that is only 2 credit hours. 2. Why is there a desire to keep making this class more difficult? Did you guys once feel it was too easy? I don't understand. Looking back at past semester EF 230 websites it looked like a joke in comparison to our class. 3. This class has little value to most everyone that takes it. Some Mech/Aerospace people will need it for projects in the future. As a chemical engineer I will need this class one more time for a certain unnamed professor that everyone loathes. And I realize she is the only reason ChemEs are even required to take this. So maybe that's who I should be whining to. 4. The amount of time that has to be put into this class is distracting us from our major classes which are much more applicable to US specifically. Even if this class were of much value, even if MATLAB was a program used outside of the university setting (and it is not, and everyone knows it) its a generic class aimed at every engineering student. 5. Building off my previous point. With HOPE scholarship being changed to a cap of 120 hours, every hour is now of more value. These are two hours I feel are completely wasted and not applicable at ALL in advancing my education. As a Chemical engineer, I will be using HYSYS for my senior porject(s) and its even used in industry. Why can't I take a class learning more about that? Why don't you guys go ask most employers what programs are most sought after in new engineering graduates and teach THOSE instead? 88.  The length of exams. 89.  The only thing was that when we were given review problems before our test, a lot of the time they weren't very relevant. A couple of the test I got the review down packed and did not do well on the test. I personally at least feel like a test review should cover most of the material on the test. 90.  Some of the exams seemed a little difficult considering the experience the class had had in those topics. Not a big deal overall (at least to me). 91.  Just a little repetitive, and spent a few days on things I have never seen/used again. 92.  Sometimes I felt like we weren't prepared enough for the hw. That is, sometimes it seemed like there was a little gap between what we were trained to be capable and what the hw was asking. More work than a 2 hour class should be. 93.  some test questions are vague 94.  It tried to cover way too many concepts 95.  learned some things i dont feel was needed. 96.  I felt like the class was more concerned about making the grades then mastering the concepts that will be useful down the road. A lot of busy work for a 2 hour class. 97.  felt rushed repeatedly on exams, and rarely was able to finish 98.  Too many syntax and usages, but this is a flaw with programming languages in general. I guess I just don't have the programming mindset. 99.  I dont like the attendance grade, especially when everything is online. I dont think its neccessary if you understand the material to go to class, it should be recommended and maybe rewarded with some extra credit but not mandatory. 100.  nothing stands out as obviously wrong or detrimental. 101.  The exams were much more difficult than the examples we did in the homeworks and in class 102.  I'm not a fan of Matlab really but I will live; however, the pace of the labs were a little quick. I feel like some info I missed. 103.  There was a lot of information being thrown at us all at once in many cases, especially when one exam covered both image/audio formatting and whatnot AND complicated differential equation solving. It was a bit too broad. 104.  While I had no problem with the test format I often thought that even with a good working understanding of the material that I had trouble completing the tests in the required amount of time. 105.  a lot of projects hahaha 106.  Nothing really. 107.  Nothing bad really stuck out, good class overall. 108.  Repeated too much of the material from EF 105. It could have covered more new topics. 109.  I don't really have any complaints.

Make at least one constructive suggestion on how this class might be improved. 'Free food' or 'Cancel the class' are not constructive.

1.  I would have liked to see more of the Simulink tool in action. 2.  Make the homework more about writing matlab code than the multiple choice questions. 3.  not sure what to tell you, this class is well setup. 4.  More emphasis should be placed on logic and why you use the code that you do for each task instead of just memorizing what code to write (specifically for ODE45). 5.  Projects that reinforce what we have learned and don't make use doubt our matlab abilities. 6.  It would help if you provided somewhere on the site for students to upload things like wav files. I know this would have helped on the slideshow project, and while I know I probably could have found a place like this online, I ran out of time looking. 7.  Work a little bit more problems that are similar to homework. If the speed of class was a little bit slower it would help as well. 8.  If you have a good final project, the actual final should not be necessary 9.  spend more time on things like functions and get rid of all the useless labs at the end of the semester. 10.  Spend more time explaining the process of programming logic. 11.  If you finished the homework the day it's assigned, you can get 5 pts extra. (will help cushion wrong answers) 12.  Slowing down a bit. 13.  It became somewhat of a hassle to have a homework due every class period (for the most part), maybe making slightly longer homeworks that cover more topics and are only due once a week or once every two weeks would make people more willing to give their best effort and take the assignment seriously 14.  N/A 15.  The last few lectures seemed to just be time fillers. I think I would have rather had a few quick review lectures to prepare for the final exam. And Free food would also be nice 16.  Allow for more freedom with projects in terms of selecting what to do (like the slideshow and final projects). 17.  the GTA could be a little slower....so others would have time to understand... 18.  The projects seemed to be more difficult than they needed to be. I think the class would benefit if the projects were broken up into smaller parts with separate deadlines. 19.  Pass along all the general MATLAB tips as you think of them instead of telling us at the end of the year. It could be useful to do a module type structure like the EF 151/2 classes do, incorporating some examples from the major engineering disciplines that would use MATLAB. It would help us in the future. 20.  Allotted "project work time" slots in lab were typically only 15-20 minutes long (except for the final project). I felt like I couldn't really do very much in these time periods and many people just ended up leaving in the middle. 21.  I think the first class should be a brief introduction/history to computer languages, and an overview about why Matlab is important, and why Matlab is chosen as the required language to know. 22.  I think maybe there should be more examples of real life applications of coding. Though it may not be able to cover all fields of engineering, I believe more application examples would be helpful. 23.  More review for tests 24.  Honestly can't think of anything. 25.  Separate the lab and the lecture. The material is too dense to reasonably expect practice during the short time period given. 26.  I would like to seem maybe another class to follow this one maybe as an elective to help solidify all that was learned and expand. 27.  See above comments section. 28.  Make the hw worth less and the projects worth more. The amount of time put into the projects is not reflected accurately in the grading scale. 29.  The exams were too hard. If you didn't go to help session, The exams were almost impossible. 30.  Just better preparation for the tests 31.  Make people follow along in matlab and turn in code as HW/participation grade 32.  Explain fmincon alot more. I still have no idea how to use it. 33.  I feel like this last couple weeks of class have been mostly about self-interest topics like java and other non-matlab related programs. Maybe instead of taking attendance as a normal grade, make it like an extra credit participation grade since the topics aren't required for the class. 34.  I think the GTAs for each help sessions did an awesome job. But having more than 1 GTA during "busy" days would help them out and help students out better. 35.  less projects 36.  Just making sure you understand that not everyone is on the same level in this class so some people need more help than others understanding the material. 37.  Change the format of the class back to what it was 2 years ago or make the exams worth less percentage wise and make the projects worth more. Or make the course a 3 hour course. 38.  While I know not everything in Matlab can always be covered, a little more attention to the commands/process that are needed to do some of the homework questions and the projects would be nice. 39.  Write the exams in the same format as the way its taught in class. In class examples and in the homework we just focus on examples, but on the exams its overwhelming trying to process what we have learned and apply it to a hard topic. Also, I think we need to have the projects weigh more than the exams. Exams take up one class period and about one day of reviewing, but our projects take more than 10 hours of work, including the time we spend in the help session. 40.  I think the class would be better off if it spent more time on debugging. I am still trying to grasp all the concepts of debugging, and I think this area of matlab could be covered better. I think the test should allow you to submit your test cases, just so you can see how the student went about solving the problem, because there is always more than one way to solve a problem. 41.  maybe have more student/TA interaction during the class period 42.  Make class a little more interesting so it would be easier to pay attention for an hour and fifteen min. 43.  I would have liked to go over more real-world applications. Also, I think homework extra credits (for doing it early for example) would be nice, since I forgot about one of mine and it was hard to make up for those lost points. 44.  I put a lot of time into this class, a lot more than I actually felt like I needed. I had to spend more time working on matlab than I did my physics class. 45.  change the way the tests work people lose alot of points because the stupid system doesn't read their code right 46.  Change the test format. 47.  covered way too much in not enough detail to actually get to understand and use everything, make the homework problems actually useful the multiple choice that was picky and meant to trick us doesnt help us learn 48.  Make it 3 hours and go slower but learn more material 49.  Once we get to some of the more complex calculations, a simple step-by-step breakdown of what to do would be very much appreciated. It can be a little confusing without that. 50.  Cover the sorts of functions that will be necessary to complete projects 51.  I think they should all grade the same. On my project 3 stephen graded it and took off 10 points for something and everett looked at it and said he would not have taken any off 52.  I think having projects that you can understand in a useful application is better than creating a specific code that makes something like the polygon project. 53.  It is sometimes difficult to work problems in homework and exams, that seem rather simple when the TA's go through them. I feel as though more group work and a slightly slower pace of class would help reduce the severity of this issue. 54.  I think we should have smaller classes with that meet for 50 minutes but three times a week. That way it is easier to pay attention. 55.  I feel like the tests had too much to do with too little time. Lighten up on the amount of work on the tests 56.  Pre-programmed lab files with comments in place (no code in place) 57.  Adding built in help sessions. Almost required help sessions, that are just there for asking questions, therefore the TA's dont have to just strictly get through a lecture, and can slow down and just answer questions. 58.  Make the last classes useful. Otherwise, cancel them. 59.  I think this class can be improved if we had more of coding problems on the homework. 60.  Have a select answer and submit button for the homeworks that were multiple choice. Several times I clicked back to the homework page and accidentally clicked a random answer. 61.  Make it a 3 hour credit? Im not sure I think this class is well thought out. 62.  It could be improved by giving homework more related to coding and less multiple choice answers. I feel I would have done better if I would have had coding homework instead. 63.  Teach functions even earlier than they already are. They were hard to understand and it took practice to get used to them but they were extremely useful. 64.  This class is near perfect. I really enjoy the way it's setup. 65.  Multiple choice tests. Or tests more like the homeworks. 66.  You could make "suggestions" on good MATLAB book(s) to purchase. It's nice not to have a "required" book, but it might be good to reference one when needed. I almost purchased a book to help me, but I didn't know what was a good one... so I never did. 67.  Everett tutor Stephen, Stephen teach for Everett 68.  I liked the change from multiple choice exams to coding problems. I think it's a better indicator on how well we are able to apply what we learned in class. 69.  make it a MWF class maybe or have slightly more informative notes on the website 70.  Make it worth 3 credit hours - I put in as much work in this class as some of my engineering classes. 71.  Maybe allow more freedom for earlier projects 72.  I would have liked to do more in class. It gets boring to just listen to functions and their uses being listed, and it's easy to zone out and have to go back and read the whole lab. I liked when we had small things to accomplish during class so that I kept more busy and because I learn by actually doing things, rather than reading about them. 73.  To make exams a bit easier, when we are given practice problems, you could give us the code answer UP UNTIL the exam day. 74.  Make it 3 credit hours or lighten the load. It is frustrating to have to put so much time into a 2 credit hour class. Also, Everett should try to speak to students on their level, not his graduate level programming speak. 75.  have more basic questions that require code to figure out on the homework instead of so many multiple choice questions. because we may not be able to get to the material in the lab that some of the multiple choice questions cover. 76.  Maybe make exams a little shorter, or have the problems not as time consuming. Maybe have 1 group project or presentation in the semester? 77.  I would make one less project, it seemed like once a project was turned in it was time to start the next one, I would have liked a little more down time between each one so it wouldn't become the same thing over and over and over. 78.  A book or another reference material would have helped me out a lot. 79.  maybe the help sessions could have more than one person help at it. even if its not another TA it could be someone who has had the class before or something. 80.  I like that the exams were challenging, but I think they should be slightly less challenging. 81.  It is better to let student read the knowledge online at home,then finshed the homwork. After that when it is class time, give some new tasks to student or let student work on the projects. Because student need GTAs' hlep when they are doing thier work, but class time is waste on tallking about the knowledge. 82.  take more time on each lab, also maybe recording the class would be a good idea... on the "live@ut" website. 83.  Raise the participation percentage to count more towards the grade. 84.  A re-working of the exam format would not be entirely out of the question. As this is only a 2 hour credit course, the exam difficulty presented was entirely too high. As a result, exam problems were too involved and the amount of time present to complete the exams was not adequate. 85.  accepting late or early deadlines for the homework assignments by 1 day? I blanked and forgot about one homework and missed it by a couple of hours. that zero dropped my entire homework grade. 86.  go in depth on needed stuff rather than showing bits of unneeded stuff 87.  I think the only constructive suggestion I can make IS to cancel this class. But since I know that's not going to happen. I simply ask to quit trying to up the difficulty of it. I still have friends that have to take this class, and I feel sorry for them. It's not fair that we have 5 projects when 2 years ago there was only one. Are there going to be 10 two years from now? This class is growing out of hand and needs to be put on a leash. 88.  A list of functions that one would need to learn for each test, whether it be a separate list or a new heading in each lab. 89.  A lot of the times on the lab pages, they would give an example matlab program. On this matlab program they would cover multiple examples. Sometimes these examples would blend together and I wouldn't quite follow what was going on in them. It would at least help me if each of these examples was made into its own page. 90.  A class-wide team project, or a project of 2-3 large teams in a competitive setting might be a fun activity for students. 91.  Add a section on AutoCad or something similar. 92.  Explanations of functions, subplots, and a few other functions like fsolve and fmincon could be improved. I felt like I was learning it completely on my own--maybe a little less coding and more pseudocode to drive the outline of how it works on certain days. It's especially annoying to have a problem with it and search through to find the problem based on material we've only just gotten into. 93.  alot more practice prblms that are not required but are optional. maybe for extra credit. 94.  Reduce the number and depth of some topics 95.  spend more time on harder topics. allow a few days for one lab maybe. 96.  I felt like a lot of the time I was just copying the .m files trying to get all of it rather than listening to what was going on. Maybe I just need to be a better multi tasker but somehow fixing this would help. 97.  work on efficiency in problem solving 98.  Splurge on some quieter air conditioners. While my hearing is by no means as sharp as an owl's, it's still hard to hear from the mid section of the room. 99.  multiple choice tests 100.  Could use some review of material regularly in schedule 101.  Make the exams a more general understanding of the use of matlab and its commands instead of a death trap for non computer geeks... 102.  Notes. More notes. When I see a line of code that does not have notes I tend to get annoyed because I am not 100% sure what it does. Some of the examples in class lacked proper annotation and I got a little frustrated with it. 103.  Make sure the GTAs don't step on each other's toes. Stephen and Everett seemed to not exactly get along a lot of the time. 104.  Possibly review the testing format or add late credit for homework assignments. 105.  i think a more 50/50 test with multiple choice and the code writing would be helpful 106.  Maybe make part of the programming portion of the exam extra credit. 107.  Get project and test grades back a little sooner. 108.  Review the old material faster so that it gets more in-depth with programming. 109.  I think the section on other programming languages should be expanded.